feat(storybook): Remove consideration of mjs from docgen plugin #11346
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We created out Storybook framework package by starting with the official framework package for React Vite.
Included in this is a Vite plugin for React Docgen, which is used by Storybook to know what the "controls" are (aka props) for a given component.
This is simply a QOL thing —
With docgen:
Without docgen:
With or without docgen, in order to be able to have interactive controls, you still need to configure them.
Docgen is mostly just used for automatic argType inference.
The docgen plugin that we originally included in our framework package matches components in
mjs
,tsx
, andjsx
files.tsx
andjsx
are obvious requirements, and we didn't give any additional thought to the inclusion ofmjs
, though it now seems that if you do have any.mjs
files that aren't components, it'll completely break your ability to load stories, as discovered by @simoncrypta.Therefore, this PR simply removes the inclusion of those files.